Acquiring Suite (POS + TMS)

CashCom Acquiring Suite - software suite for bank acquiring on POS terminals with a full terminal management system (TMS, Terminal Management System).
The solution covers the entire lifecycle: from key and parameter preparation to remote monitoring, device park management, software updates, receipt templates, and interfaces.

Supported:

• OS PayDroid 11–13;
• a wide range of PAX terminals (A77, A8900, IM30, A6630, etc.);
• Neptune SDK, EMV (contact + contactless);
• ISO 8583 (including SmartVista / BPC profile): purchase, authorization/completion, cancellation, refund/partial refund, balance inquiry, P2P, reconciliation, reversal.

Typical Use Cases

• A bank or fintech provider deploys its own acquiring solution on a fleet of PAX POS terminals.
• A large retail chain wants a single TMS to manage hundreds/thousands of terminals, including with multiple acquiring banks.
• Payment processing builds a multi-merchant/multi-acquirer infrastructure and needs a ready-made application + TMS instead of developing from scratch.
• Replacement of outdated TMS/software on terminals with a more flexible system featuring a UI/receipt editor and proper telemetry.

Overall Architecture

Logical diagram:

• POS Terminals (PAX PayDroid)
  – CashCom Acquiring client application;
  – EMV core/Neptune SDK;
  – printer drivers, CTLS readers, PIN pads, scanners.

• Acquiring Backend
  – ISO 8583 adapter to the bank/payment processor host (including SmartVista/BPC profile);
  – routing and retry services;
  – reconciliation and back-office integration services.

• CashCom TMS
  – management of the structure "bank → merchant → point → terminal";
  – storage of EMV/Neptune/ISO parameters;
  – key and certificate management;
  – monitoring and telemetry;
  – OTA software and configuration updates;
  – UI and receipt template editor;
  – role model and auditing.

All interactions POS ↔ Backend ↔ TMS occur over secure channels (TLS/mTLS), critical messages are signed/verified.

Functionality of the POS Application

Supported Operations (ISO 8583 / SmartVista)

• Purchase (Purchase / Sale).
• Pre-authorization (Authorization / Pre-Auth).
• Completion (Completion / Capture) - full and partial.
• Cancellation (Void / Reversal before sending to clearing).
• Refund (Refund) - full and partial.
• Balance Inquiry (Balance Inquiry).
• P2P transfers (according to specifications, via the bank's ISO 8583 profile).
• Reconciliation/closing of the shift (Reconciliation / Batch / Settlement).

If necessary, the following can be added:

• CashBack (if allowed by the scheme/acquirer).
• Tips / Adjust Tips (tips).
• Split Bill (bill splitting).
• EMVCo QR (CNP schemes and local standards).

All operations are implemented considering the typical requirements of schemes and SmartVista: correct handling of reversals, resending, batch reconciliation, uniqueness of RRN/STAN, etc.

Cards and Schemes

• Cards Visa, Mastercard, MIR, UnionPay, etc. (subject to parameters, certifications, and permissions).
• EMV core (contact + CTLS), support for CLESS scenarios, CDCVM (if necessary).
• Ability to connect custom/local schemes (local cards, co-brands) through separate AID/EMV parameter profiles.

UX / UI on the Terminal

• Multilingual interface: English, Russian, Turkmen out of the box.
• Quick language change by the user (icon/button).
• Screen forms (amount, payment options, PIN/signature entry, merchant selection, etc.) - various types of scenarios are implemented, managed from TMS.
• Branding support: logo, colors, background image, slogans.
• Ability to display additional hints, advertisements, promotional messages (banners between transactions).

Localization

• Ready language packs: EN/RU/TM.
• Ability to add a new language pack without software modifications.
• Management of localized templates through TMS.
• Support for different date/time formats, separators, currency symbols.

Working with Printers and Receipts

• Support for built-in PAX printers and external ones (Bluetooth, BLE, USB, LAN).
• Receipt templates (layout, fields, barcodes/QR codes, logos) are configured in TMS and applied to a group of terminals.
• Different types of receipts can be created: customer, merchant, reconciliation receipt, slip with additional data.
• Support for reprinting, "service receipt," custom footer messages.

Device Security

• Cryptographic keys are protected at the level of a secure hardware environment (Secure Element) provided by the Neptune SDK of PAX terminals. Keys are generated, stored, and used within a secure area, never leaving it in plaintext, complying with PCI PIN and PCI PTS standards.
• Two-way terminal registration (input of TMK key in parts, KVCofKTM verification).
• Use of separate keys to protect all messages Terminal ↔ TMS, forming/verifying digital signatures in both directions.
• Access to settings and service functions is restricted by password/role.

TMS (Terminal Management System)

Management of Structure and Device Park

• Model: Bank → Merchant → Point of Sale → Terminal.
• The client can define nested subdivisions, regions, brands.
• It is visible which terminal is at which point, its status, software version, and parameter set.
• Groups/tags: for example, "Moscow," "Flagship Stores," "Test Circuit" for selective deployment.

Monitoring and Telemetry

• Online map of terminals and status (online/offline, last contact).

• Metrics: signal level, battery (for mobile), temperature, application/parameter version, peripheral device statuses.

• Event logs (errors, communication failures, non-standard host responses).

• Alerts: via e-mail, messengers, webhook - for example, "terminal has not communicated for N minutes," "series of failures," "software version change out of schedule."

OTA Updates (Software, Configuration, Languages)

• Application version management, configurations, languages, media resources.

• Update scheduling: by schedule, by group, "canary" deployment to part of the fleet.

• Ability to roll back version.

• Deployment logs: which terminals were successfully updated, where the error occurred.

UI Management and Receipt Templates

• Enabling/disabling scenarios, parameters;

• Creating new receipts, modifying current templates, integrating into scenarios.

Access Management and Audit

• Roles: system administrator, bank operator, merchant operator, technical support, etc.

• Granular permissions (who can change keys, perform deployment, modify UI, etc.).

• Logging all actions in TMS (who/what changed, applied to which devices).

• Ability to integrate with corporate authorization system (SSO, OIDC/SAML).

Integrations and API

• ISO 8583 host (SmartVista/BPC - out of the box), other hosts - via connector.

• REST API for integrations:

• Webhook notifications for events: shift closure, anomalies, suspicious transactions.

Security and Compliance

• Channel encryption (TLS/mTLS), certificate verification.

• Use of separate keys to protect all messages Terminal ↔ TMS, generation/verification of digital signatures in both directions.

• Logs and audit in a separate secure environment.

• Ability to integrate with HSM for key generation/storage.

Operation and Scalability

• Deployment on-prem or private cloud.

• Horizontal scaling of TMS and backend (multiple instances, load balancer).

• Logging to a centralized storage.